VBS2Combined Arms will not connect to VBS2
- VBS2Combined Arms will only connect to VBS2 when you reach the mission briefing screen of a scenario. This will occur after you have hit the ‘Connect’ button in the network lobby of VBS2.
- Check the VBS2Combined ArmsIPAddress.dat file in the root directory of your VBS2 installation. Ensure that the contents of this file define an IP address of the machine that is running VBS2Combined Arms. If that file is not present, then ensure you are running VBS2Combined Arms on the same machine as VBS2 is running on.
- Ensure that no firewall is preventing socket communications between VBS2 and VBS2Combined Arms.
- Use the netstat –a command from the windows command prompt to check if any other programs are causing a conflict with the sockets that VBS2Combined Arms is using. If a conflict has occurred (consult the list of port numbers used at the beginning of this document), then you should close down the other application which is conflicting with VBS2Combined Arms and run VBS2Combined Arms again.
- If you have IPv6 installed on your system, ensure that IPv4 is also installed and that you are running VBS2Combined Arms with the -Djava.net.preferIPv4Stack=true before the -jar flag in the command line.